Remove duplicate run call for ApplicationRunner#1887
Conversation
Removed duplicate runner.run(Component) call. In python wamp pubsub basic example.
|
Thanks for this, @JavierSab — nice catch! 🙌 The change is correct: that second A few small process bits before we can merge. Up front: some of these aren't So I filed: #1889 And for your specific issue this PR fixes: #1888
No tests needed for an example-file cleanup like this. Once the issue reference |
|
@JavierSab thanks for adding an audit file! I now approved to run CICD, let's see. because, sorry, there is still a small itch with the audit file contents, it doesn't reference the issue #1888 I added in I still approved to run, since I wanted to give you some "positive success" feedback already, and because I want to know whether our CICD would detect the missing issue reference automatically, and fail! which it might not yet do - which would be something for us to improve then. |
|
more notes: 1. Rename the audit file (this is what's failing CI ✋)The Windows CI job is failing at checkout with: The cause is the The convention is git mv ".audit/JavierSab:patch-1.md" .audit/JavierSab_patch-1.md
git commit -m "Rename audit file to valid cross-platform name"(compare existing files, e.g. 2. Reference the issue in the audit file (+ PR)Now that there's an issue for this (#1888 — thanks for bearing with the
|
…used-type-ignore-comment
ty is run unpinned (we ride the latest release and adjust the ignore
list as it evolves). ty 0.0.53 began emitting two diagnostic classes on
existing, unchanged source that the check-typing recipe did not ignore,
so `ty check` exited 1 and Code Quality Checks went red:
- 921x possibly-missing-submodule (vendored FlatBuffers-generated code
under src/autobahn/wamp/gen/** plus a few flatbuffers.* re-export
sites in message_fbs.py / message.py / protocol.py)
- 1x unused-type-ignore-comment (src/autobahn/util.py:1062)
0 errors; all warnings. Drift, not a code regression: master was green
on 2026-06-19 with an earlier ty, and went red on a 2026-06-25 run that
pulled ty 0.0.53 (surfaced on the unrelated example-cleanup PR crossbario#1887).
Add both rules to the check-typing --ignore list. Reproduced red->green
locally with ty 0.0.53 against the cpy311 venv: 922 diagnostics/exit 1
before, "All checks passed!"/exit 0 after.
Note: This work was completed with AI assistance (Claude Code).
* start new dev branch; add audit file * Fix #1892: ignore ty 0.0.53 possibly-missing-submodule + unused-type-ignore-comment ty is run unpinned (we ride the latest release and adjust the ignore list as it evolves). ty 0.0.53 began emitting two diagnostic classes on existing, unchanged source that the check-typing recipe did not ignore, so `ty check` exited 1 and Code Quality Checks went red: - 921x possibly-missing-submodule (vendored FlatBuffers-generated code under src/autobahn/wamp/gen/** plus a few flatbuffers.* re-export sites in message_fbs.py / message.py / protocol.py) - 1x unused-type-ignore-comment (src/autobahn/util.py:1062) 0 errors; all warnings. Drift, not a code regression: master was green on 2026-06-19 with an earlier ty, and went red on a 2026-06-25 run that pulled ty 0.0.53 (surfaced on the unrelated example-cleanup PR #1887). Add both rules to the check-typing --ignore list. Reproduced red->green locally with ty 0.0.53 against the cpy311 venv: 922 diagnostics/exit 1 before, "All checks passed!"/exit 0 after. Note: This work was completed with AI assistance (Claude Code).
|
Merged — thank you, @JavierSab! 🎉 Your fix is in And to close the loop on the one red CI workflow you saw: that failure was entirely on our side, not your change. 🙏 see #1892 and #1893 The failing job was Code Quality Checks → "Code static typing (via ty)", which is completely independent of the example you fixed. We run Astral's |
Removed duplicate runner.run(Component) call. In python wamp pubsub basic example.
Description
Removal of a duplicate
run()line in one of the WAMP simple pubsub client examples.Related Issue(s)
Closes or relates to #
Checklist
the style guidelines of this project
is effective or that my feature works
updated the changelog
in this PR
AI Assistance Disclosure File
file at
.audit/<branch-name>.mdright in this PR. Thedisclosure file must follow the exact format and content as
described below. Your PR will not be accepted without a
disclosure file.
Example 1 file contents of your disclosure file
.audit/<branch-name>.md:OR
Example 2 file contents of your disclosure file
.audit/<branch-name>.md:Submitting code generated primarily by AI, or for which you
cannot claim human authorship, is not permitted. See
AI Policy
for details.
Example 1 OR Example 2 show the only valid two variants. You
cannot have both or none of the first two marks checked, and you
must always have the last tick checked.
Well, "must" if you want your PR to be accepted and ultimately
merged that is. Of course you are always free to
Go ahead! Fork my Day. (TM);) This is Open-source.